Availability and Accessability |
Currency |
Reliability and Credibility |
Usability and Interpretability |
Referential integrity
Compare with other Characteristic
Characteristic Name: | Referential integrity |
Definition: | Data relationships are represented through referential integrity rules |
Dimension: | Consistency |
Granularity: | Record |
Characteristic Type: | Declarative |
Implementation Form: | Rule-based approach |
Verification Metric:
The number of referential integrity violations per thousand records |
Validation Metric:
To what extent required rules have been identified and implemented to maintain the declarative characteristic in concern. |
BackgroundGuidelines
The original definitions given below formed the basis of the consolidated definition of the characteristic.
Definition: | Source: |
---|---|
The Information Float or Lag Time is acceptable between (a) when data is knowable (create or changed) in one data store to (b) when it is also knowable in a redundant or distributed data store, and concurrent queries to each data store produce the same result. | ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. More from this source |
Assigning unique identifiers to objects (customers, products, etc.) within your environment simplifies the management of your data, but introduces new expectations that any time an object identifier is used as foreign keys within a data set to refer to the core representation, that core representation actually exists. | LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation. More from this source |
i.e. integrity rules. Data follows specified database integrity rules. | PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a. More from this source |
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
Guidelines: | Scenario: |
---|---|
Implement and maintain foreign keys across tables (Data sets) | (1) Implementation of foreign keys |
Implement proper validation rules/Automated suggestions of values based on popular value combinations, to prevent incorrect references of foreign keys | (1) The attribute Customer_Zip_Code of the Customer relation contains the value 4415, instead of 4445; both zip codes exist in the Zip_Code relation |
Implement validation rules for foreign keys of relevant tables in case of data migrations | (1) Error logs are generated for foreign key violations. |
Implement proper synchronising mechanisms to handle data updates when there are concurrent operations or distributed databases. | (1) Locking mechanisms to data objects while being updated |
Ensure the consistency of the data model when changes are done to process model (software) | (1) Data dictionary provides the FDs and CFDs |
Availability and Accessability |
Currency |
Reliability and Credibility |
Usability and Interpretability |
Leave a Reply
Be the First to Comment!
You must be logged in to post a comment.